Method, system and computer product for performing failure mode and effects analysis throughout the product life cycle

ABSTRACT

A method for performing failure mode and effects analysis throughout the product life cycle. The method comprises receiving incident data from a requestor. The incident data includes a requestor product and a requestor fault mode. A shared failure mode and effects analysis database is accessed and searched for an existing entry that includes the incident data. The contents of the existing entry are transmitted to the requestor in response to locating an existing entry.

BACKGROUND OF INVENTION

The present disclosure relates generally to a method for distributeddesign and field service of a product and in particular to a method ofdeveloping and utilizing an electronic failure mode and effects analysis(FMEA) for performing design and field service of the product.

FMEA is a methodology for determining the root causes of defects inmanufacturing processes and products. FMEA can be applied during thedesign phase of a product or process to identify potential fault modesor defects that may cause product or process failures. The FMEAmethodology emphasizes defect prevention by examining all potentialcauses of a defect; the likelihood of these causes occurring andresulting in the defect, and ways of preventing these causes fromoccurring and resulting in the defect. The causes of defects in productsmay be defects in components that may be caused by sub-componentdefects. A typical FMEA includes a hierarchical list by component typeof what happens to the overall product and the component when each partof the product fails. The hierarchy can include levels such as majordivision, system, sub-system, assembly, sub-assembly and part. The riskof potential fault modes are prioritized based on an estimated frequencyof detection and severity. The probability of certain defects may beestimated by applying statistics to product or process histories.Otherwise, probabilities may be estimated based on experience.

Typically, in product or process design, an individual or a team isassigned to create a FMEA report or document. Team members can includerepresentatives from disciplines such as engineering, purchasing,finance and field service. Performing FMEA can require that severalexperts assemble in one location for significant periods of time togenerate the FMEA data. In a series of meetings, team members brainstormto develop a list of potential defects, their effects (e.g., severity),and potential causes of the defects. In addition, the defects areprioritized according to an estimated risk. One or more of the teammembers take notes during the session. The work is often divided upamong the team members to be performed outside the meeting. The workperformed outside the meeting is then discussed and validated in themeetings. The team comes to consensus on whether each potential defectand the effects and causes of the defect are correct, and how much riskthere is for each. After the meetings have concluded, the resultingconsensus information is gathered into a FMEA report or document. Atypical FMEA report can contain hundreds of entries. Utilizing a paperprocess for generating a FMEA report can make it difficult for the FMEAreport to be disseminated, maintained and updated. The FMEA team canalso document suggested corrections to prevent the defects or faultsfrom occurring during customer use of the product or process. This datacan be added to the FMEA report. In an extension of the process the datain the FMEA is augmented by corrective actions for each fault mode, andthe resulting chart is called a failure mode effects and criticalityanalysis (FMECA).

SUMMARY OF INVENTION

One aspect of the invention is a method for performing failure mode andeffects analysis throughout the product life cycle. The method comprisesreceiving incident data from a requester. The incident data includes arequestor product and a requestor fault mode. A shared failure mode andeffects analysis database is accessed and searched for an existing entrythat includes the incident data. The contents of the existing entry aretransmitted to the requestor in response to locating an existing entry.

Another aspect of the invention is a system for performing failure modeand effects analysis throughout the product life cycle. The systemcomprises a network, a user system in communication with the network, astorage device including a shared failure mode and effects analysisdatabase and a host system. The host system is in communication with thenetwork and the storage device and the host system includes electroniccollaboration software to implement a method comprising receivingincident data from a requestor on the user system. The incident dataincludes a requestor product and a requestor fault mode. The sharedfailure mode and effects analysis database is accessed and searched foran existing entry that includes the incident data. The contents of theexisting entry are transmitted to the requestor on the user system inresponse to locating an existing entry.

A further aspect of the invention is a computer program product forperforming field service of a product. The computer program productcomprises a storage medium readable by a processing circuit and storinginstructions for execution by the processing circuit for performing amethod. The method comprises receiving incident data from a requestor.The incident data includes a requestor product and a requestor faultmode. A shared failure mode and effects analysis database is accessedand searched for an existing entry that includes the incident data. Thecontents of the existing entry are transmitted to the requestor inresponse to locating an existing entry.

Further aspects of the invention are disclosed herein. The abovediscussed and other features and advantages of the invention will beappreciated and understood by those skilled in the art from thefollowing detailed description and drawings.

BRIEF DESCRIPTION OF DRAWINGS

Referring to the exemplary drawings wherein like elements are numberedalike in the several FIGURES:

FIG. 1 is a block diagram of an exemplary system for performing fieldservice of a product;

FIG. 2 is an exemplary embodiment of a database layout for performingfield service of a product;

FIG. 3 is a block diagram of an exemplary embodiment of an overallprocess for utilizing a FMEA database during product design and fieldservice;

FIG. 4 is a block diagram of an exemplary embodiment of a process forperforming field service of a product utilizing a FMEA database; and

FIG. 5 is an exemplary embodiment of a user interface for searching aFMEA database for a fault mode in a product.

DETAILED DESCRIPTION

One embodiment of the invention is a method for developing a FMEAdatabase during the product design process, and for subsequentlyfacilitating the field service of a product. In an exemplary embodiment,an electronic interface to a FMEA database is made available on aweb-site, along with an on-line dialog that extracts information fromthe product experts (e.g., the original design engineers and experiencedfield engineers). The information from all the product experts isreconciled and provided for dissemination, review and subsequentupdating of the FMEA database. The same web-site may contain access tosearch features that can be used to generate references and supportingdocumentation. In addition, a diagnostic capability is provided thatallows end-users in the field (e.g., customers and remote diagnosticengineers) to search on effects, or symptoms, and results in the displayof the associated corrective actions. New information provided byend-users in the field can be added to the FMEA database to track theproduct during field service. Product design team members do not need tobe co-located and customers and field engineers do not need to meet orotherwise simultaneously access the system in order to identifydiagnostic information. Additionally, the same system can be used tostore product reliability information throughout the product life cycle,eliminating the need for multiple local copies of information and forservicing inconsistencies.

FIG. 1 is a block diagram of an exemplary system for performing fieldservice of a product. The system of FIG. 1 includes user systems 102through which an end-user can make a request to an application programon the host system 104 to access particular records stored on thestorage device 108 in a FMEA database. Additionally, these requests foraccess to the FMEA database could come from a computer applicationrunning on the host system 104. In an exemplary embodiment, end-userscan include product design team members or product experts located in adesign or manufacturing site, a field service engineer located at afield office, an administrator, and a customer located at a customerlocation. The design team members can be physically located in one ormore locations. In an exemplary embodiment, the host system 104 executesprograms that provide access to one or more FMEA databases related toparticular products. The user systems 102 can be directly connected tothe host system 104 or they could be coupled to the host system 104 viathe network 106. Each user system 102 may be implemented using ageneral-purpose computer executing a computer program for carrying outthe processes described herein. The user systems 102 may be personalcomputers or host attached terminals. If the user systems 102 arepersonal computers, the processing described herein may be shared by auser system 102 and the host system 104 by providing an applet to theuser system 102.

The network 106 may be any type of known network including a local areanetwork (LAN), a wide area network (WAN), an intranet, or a globalnetwork (e.g., Internet). A user system 102 may be coupled to the hostsystem 104 through multiple networks (e.g., intranet and Internet) sothat not all user systems 102 are required to be coupled to the hostsystem 104 through the same network. One or more of the user systems 102and the host system 104 may be connected to the network 106 in awireless fashion and the network 106 may be a wireless network. In anexemplary embodiment, the network 106 is the Internet and each usersystem 102 executes a user interface application to directly connect tothe host system 104. In another embodiment, a user system 102 mayexecute a web browser to contact the host system 104 through the network106. Alternatively, a user system 102 may be implemented using a deviceprogrammed primarily for accessing the network 106 such as WebTV.

The host system 104 may be implemented using a server operating inresponse to a computer program stored in a storage medium accessible bythe server. The host system 104 may operate as a network server (oftenreferred to as a web server) to communicate with the user systems 102.The host system 104 handles sending and receiving information to andfrom user systems 102 and can perform associated tasks. The host system104 may also include a firewall to prevent unauthorized access to thehost system 104 and enforce any limitations on authorized access. Forinstance, an administrator may have access to the entire system and haveauthority to modify portions of the system and a customer may only haveaccess to view a subset of the FMEA database records for particularproducts. In an exemplary embodiment, the administrator has the abilityto add new users, delete users and edit user privileges. The firewallmay be implemented using conventional hardware and/or software as isknown in the art.

The host system 104 also operates as an application server. The hostsystem 104 executes one or more application programs to provide accessto the FMEA database. Processing may be shared by the user system 102and the host system 104 by providing an application (e.g., java applet)to the user system 102. Alternatively, the user system 102 can include astand-alone software application for performing a portion of theprocessing described herein. It is understood that separate servers maybe used to implement the network server functions and the applicationserver functions. Alternatively, the network server, firewall and theapplication server can be implemented by a single server executingcomputer programs to perform the requisite functions.

The storage device 108 may be implemented using a variety of devices forstoring electronic information such as a file transfer protocol (FTP)server. It is understood that the storage device 108 may be implementedusing memory contained in the host system 104 or it may be a separatephysical device. The storage device 108 contains a variety ofinformation including a FMEA database that includes both a consensusFMEA database, and one or more end-user personal FMEA databases. Thehost system 104 may also operate as a database server and coordinateaccess to application data including data stored on the storage device108. The consensus FMEA database and end-user personal FMEA databasescan be physically stored as a single database with access restrictedbased on user characteristics or they can be physically stored in avariety of databases including portions of the database on the usersystems 102 or the host system 104. In an exemplary embodiment, the FMEAdatabase is implemented using a relational database system and thedatabase system provides different views of the data to different usersbased on user characteristics. In an exemplary embodiment, the FMEAdatabase is initially populated by entering the FMEA information as itis being developed by the product design team. In an alternate exemplaryembodiment, the FMEA database is initially populated by importing datafrom an external system containing a consensus FMEA database createdduring the design process.

FIG. 2 is an exemplary embodiment of a layout of a FMEA database forsupporting design and field service of a product. In an exemplaryembodiment of the invention, the layout of the case records contained inthe end-user personal FMEA databases are the same as the layout for therecords contained in the consensus FMEA database. Database fields, usingdesign terminology, are listed under the heading “Design Terminology”244 in FIG. 2. The corresponding names of the fields, if they differ, infield service terminology are listed under the heading “Field ServiceTerminology” 246 in FIG. 2. In an exemplary embodiment of the invention,a single FMEA database is utilized for supporting both product designand field service. Referring to the database fields in FIG. 2, the fieldlabeled product 202 is the top-level physical product of interest (e.g.,computer monitor, rolling mill). The component 204 is a subset of theproduct 202 such as a subsystem, assembly, or part depending on thelevel of the hierarchy of parts. In an exemplary embodiment, fault mode206 is an observable functional defect of the system. The fault mode 206may include a fault code indication if the product has built-in faultdetection. In field service terminology, the fault mode 206 correspondsto the customer complaint 234. The exemplary FMEA database layoutdepicted in FIG. 3 also includes cause 208 which is the root cause ofthe problem at the lowest level of detail that is of interest. Theprimary effect 210 and product level effect 212 relate to theconsequences of the cause 208. The primary effect 210 is the consequenceof the cause 208 at the lowest level of interest (e.g., component) andthe product level effect 212 is the consequence of the cause 208 at thehighest level of interest (e.g., system). In field service terminology,primary effect 210 corresponds to component symptom 236 and productlevel effect 212 corresponds to product level symptom 238.

The exemplary embodiment of a FEMA database layout depicted in FIG. 2also includes a field for severity 214 data. Severity 214 is a severityrating, according to a quantitative measure, of the fault, if it occurs.It can be utilized as an indication of the seriousness of the defect.The occurrence 216 field in the FMEA database is the rate or likelihoodof occurrence of the fault according to quantitative measures.Detectability 218 is the accuracy of the best available indicator of thefault or a physical measurement of the fault. Maintainability 220 is ameasurement of the ability to fix the fault once it is detected. Dataavailability 222 is an index of the degree to which the fault isactually being measured (directly or indirectly). Notes 224 includesfreeform text relating to the information contained in the databaserecord. The measurement 226 field includes the best sensor used tomeasure the fault or the cause. Measurement 226 corresponds to troubleshooting procedure 240 in field service terminology. The correctiveaction 228 includes a repair procedure for the fault and, as depicted inFIG. 2, it corresponds to the repair procedure (or solution) 242 infield service terminology. The FMEA database field labeled date 230contains the date that the record was updated. The FMEA database alsoincludes a risk prioritization number (RPN) 232. Alternate embodimentsof the FMEA database layout are possible depending on the specific FMEAdata required and tracked by design and field service. In an exemplaryembodiment, the same FMEA database fields are utilized for both productdesign and field service. In an alternate embodiment, the FMEA databasefields developed during product design are augmented with databasefields specific to field service.

FIG. 3 is a block diagram of an exemplary embodiment of an overallprocess for performing FMEA during product design and field service. Thedesign team members may be located at more than one physical locationand application software located on the host system 104 is utilized toperform the collaboration in order to create a consensus FMEA for theproduct. The design team members are logged on to user systems 102 thatare connected, via the network 106, to the host system 104 that includesthe FMEA collaboration application software as well as access to theFMEA database. Referring to step 302 in FIG. 3, each design team member,or product expert, independently identifies and enters into the computera list of different fault modes 206 that could occur. The data caninclude potential fault modes 206, an associated severity 214 and aprobability of occurrence 216. In an exemplary embodiment, the faultmode data is stored in a personal FMEA database associated with eachdesign team member. At step 304, the FMEA owner facilitates the creationof a consensus FMEA. The head of the product design process can beassigned to be the FMEA owner. The FMEA owner can be charged withdeveloping and maintaining the technical content of the FMEA. The FMEAowner can also serve as the moderator for the collaboration process bywhich individual experts merge their individual subsystem data inputsinto an integrated consensus FMEA.

During the collaboration process at step 304, the FMEA owner can viewwhat each design team member has entered as well as data included in theconsensus FMEA database. The FMEA owner then suggests combining variouslines of input from the design team members and leads a design teammember discussion about the combination. In an exemplary embodiment,this discussion takes place electronically. Once consensus is reached,or the FMEA owner has made a decision in the event that consensus cannotbe reached, the FMEA owner enters a new entry into the consensus FMEAdatabase. At step 306 in FIG. 3, corrective actions 228 are designed forthe highest RPN 232 items in the consensus FMEA. The RPN 232 can be anumber derived by the system as the product of severity and occurrenceindexes. For purposes such as the design of monitoring and measurementsystems, an extended RPN 232, including product detectability and dataavailability index values can also be used. The corrective actions 228are added to the consensus FMEA database. The corrective actions 228 caninclude improvement of design such as features built into the product orrepair procedures. The corrective action 228 field in the consensus FMEAmay be updated at a later time to make a design improvement or tosuggest a manufacturing process corrective action 228.

At step 308 in FIG. 3, ownership of the consensus FMEA is transferredfrom the head of the design team to an individual with product serviceresponsibility. This occurs once the design phase has been completed andthe product enters routine use. At step 310, the consensus FMEA is madeavailable to the service team, to customers and to the product upgradeteam. At step 312, suggestions for updates to the consensus FMEA arereceived and evaluated. Suggestions for updates to the consensus FMEAcan come from the service team, customers and the product upgrade teambased on information that can include new fault modes 206, new troubleshooting procedures 240 and new repair procedures 242 that have beendiscovered. In addition, new component symptoms 236 and product levelsymptoms 238 may be the basis of a suggestion to update the consensusFMEA database for a particular product. In an exemplary embodiment, thesuggestion to update the consensus FMEA is stored in a personal FMEAdatabase and evaluated in a manner similar to the consensus processdiscussed in reference to step 304 but with the field service team. Atstep 314, the consensus FMEA database is updated based on the results ofthe evaluation. Processing then returns to step 310 with the updatedconsensus FMEA being made available to the service team, customers andthe product upgrade team.

FIG. 4 is a block diagram of an exemplary embodiment of a process forperforming field service of a product utilizing a FMEA database. Theprocess begins at step 402 when a remote diagnostic engineer (RDE), orfield service engineer, receives a customer complaint 234, or fault mode206, relating to a product 202. Also included may be a component 204,component symptom 236 and/or a product level symptom 238. At step 404,the RDE searches the FMEA database for records relating to the product202 and fault mode 206. The FMEA database includes the consensus FMEAdatabase and a personal FMEA database associated with the RDE. At step406 a check is made to see if the fault mode 206 associated with theproduct 202 was located in the consensus FMEA database. Step 412 isperformed if the fault mode 206 was not located in the consensus FMEAdatabase. At step 412, the RDE creates a personal FMEA database entrythat includes the new fault mode 206 associated with the product 202along with data that can include a trouble shooting procedure 240 and arepair procedure 242 if the RDE has solved the fault. Any other FMEAdatabase fields as depicted in FIG. 2 can be included in the RDEpersonal FMEA database entry. Step 408 is performed if the fault mode206 is located in the consensus FMEA database. At step 408 the RDEreviews the consensus FMEA database entry for possible trouble shootingprocedures 240 (i.e., measurements 226) or repair procedures 242 (i.e.,corrective actions 228) associated with the fault mode 206 and product202. The RDE may access any of the fields associated with the FMEAdatabase entry to aid in fault detection and correction.

At step 410, a check is made to determine if the RDE has corrected thefault mode 206 utilizing a repair procedure 242 located in the consensusFMEA database. If the RDE has utilized a repair procedure 242 found inthe consensus FMEA database then step 414 is performed, and the RDEcreates a personal FMEA database entry that includes occurrence 216data. In an exemplary embodiment, occurrence 216 data is a counter thatis incremented. The personal FMEA database entry can also include otherinformation such as the date 230 and notes 224. Alternatively, step 416is performed if the RDE did not utilize a repair procedure 242 found inthe consensus FMEA database, as determined at step 410. At step 416, theRDE creates a personal FMEA database entry in order to document theactions the RDE performed to respond to the fault mode 206. The personalFMEA database entry can include any of the fields included in theconsensus FMEA database layout, including data such as the repairprocedure 242 that corrected the fault mode 206, fault occurrence 216rate update and product level symptoms 238 observed. At step 418, thepersonal FMEA database entry is evaluated for inclusion in the consensusFMEA. If it is determined that that personal FMEA database entry shouldbe included in the consensus FMEA (e.g., personal FMEA database entryincludes a common fault mode 206) then it is added to the consensusFMEA. In an exemplary embodiment, the consensus FMEA owner utilizes thesame collaboration process and data discussed previously to get inputfrom other team members on what entries should be included in theconsensus FMEA. In this manner, the consensus FMEA is augmented withfield service data.

In an alternate exemplary embodiment, the process depicted in FIG. 4 canbe performed by a customer, through the network 106 using a user system102, by giving the customer access to portions of the consensus FMEAdatabase for a particular set of products. The portions of the consensusFMEA database that the customer could access can include fault mode 206records that have been approved for customer access or all fault mode206 records relating to a particular product 202 that the customer haspurchased. In an alternate embodiment, a customer is directed to aparticular consensus FMEA entry by a RDE. The customer may report a newproblem by generating a customer FMEA entry to record the occurrence ofa new type of fault 242. Then, step 418 would be performed, as describedabove, in order to determine if the customer personal FMEA entry shouldbe included in the consensus FMEA. In another exemplary embodiment, theproduct upgrade team utilizes the consensus FMEA to design productimprovements for the next upgrade of the product. In this manner fieldservice data can be utilized to improve future upgrades of the product.

FIG. 5 is an exemplary embodiment of a user interface for searching aFMEA database for a fault mode associated with a product 202. Asdepicted in the user entry box 502 at the top of FIG. 5, the RDE canenter the product 202, the fault mode 206 and the product level symptom238. Any fields contained in the consensus FMEA database can be used assearch terms for the RDE to locate FMEA entries relating to a customercomplaint 234 and the fields depicted in box 502 are for examplepurposes only. In response to the data input into the user entry box502, two types of FMEA database entries are displayed. The consensusFMEA database entries 504 that match the search criteria are displayedalong with the RDE personal FMEA database entries 506 that match thesearch criteria. Any fields contained in the FMEA database entries canbe displayed and used as search fields, and the sort order can beadjusted based on user preference. For example, the FMEA entries can besorted by date 230, by increasing RPN 232 and by decreasing RPN 232 inorder to facilitate easier design or servicing. Additionally, a“fishbone” diagram may be automatically generated from the FMEA in orderto assist in root cause analysis. Other output modes are possible,including the ability to export a snapshot of a segment of the FMEA inspreadsheet format that can be utilized by users that are not remotelyconnected to the FMEA database.

An embodiment of the invention provides for a decentralized user basethat can collaborate electronically to update and utilize a consensusFMEA database from product design through product field service. Thiscan result in reduced time and level of effort required for generating aFMEA database because product experts can be located in multiplephysical locations during meetings to develop the FMEA database. Inaddition, an embodiment of the invention utilizes a single consensusFMEA database for the product design, field service and product upgradestages of the product life cycle. This can result in a reduction in timeto solve field service problems because the individuals performing fieldsupport can easily view input from the design team and other fieldservice personnel in order, to determine what type of service actionsshould be performed. Also, the use of a single consensus FMEA databasecan result in a more consistent quality of service because all fieldservice personnel will have access to the same information. Anembodiment of the invention also allows each user to keep a personalFMEA database or entries. This can result in improved local fieldservice because a RDE can record field service data for particularcustomers even if the FMEA owner has determined that the data does notbelong in the consensus FMEA. An embodiment of the invention also allowscustomers access to the consensus FMEA database either directly throughentering search terms or through a direction from a RDE to view aparticular entry. This can result in more rapid service for a customerand the ability for the product provider to provide a high level ofsupport with fewer resources. An embodiment of the invention can beapplied to a process (e.g., a customer service process) with eachprocess broken down into steps and sub-steps. This can result inimproved customer service due to an improvement in the process. Anembodiment of the present invention can be utilized for any type ofproduct including products such as industrial power distributionequipment, a turbine engine system (aircraft or power generation) andappliances.

As described above, the embodiments of the invention may be embodied inthe form of computer-implemented processes and apparatuses forpracticing those processes. Embodiments of the invention may also beembodied in the form of computer program code containing instructionsembodied in tangible media, such as floppy diskettes, CD-ROMs, harddrives, or any other computer-readable storage medium, wherein, when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing the invention. Anembodiment of the invention can also be embodied in the form of computerprogram code, for example, whether stored in a storage medium, loadedinto and/or executed by a computer, or transmitted over sometransmission medium, such as over electrical wiring or cabling, throughfiber optics, or via electromagnetic radiation, wherein, when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing the invention. Whenimplemented on a general-purpose microprocessor, the computer programcode segments configure the microprocessor to create specific logiccircuits.

While the invention has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular situationor material to the teachings of the invention without departing from theessential scope thereof. Therefore, it is intended that the inventionnot be limited to the particular embodiment disclosed as the best modecontemplated for carrying out this invention, but that the inventionwill include all embodiments falling within the scope of the appendedclaims. Moreover, the use of the terms first, second, etc. do not denoteany order or importance, but rather the terms first, second, etc. areused to distinguish one element from another.

1. A method for performing failure mode and effects analysis throughoutthe product life cycle, the method comprising: receiving incident datafrom a requestor, said incident data including a requestor product and arequester fault mode; receiving field solution data from said requestor,said field solution data including said requestor product, saidrequestor fault mode, a requestor corrective action and a requestorprimary effect; accessing a shared failure mode and effects analysisdatabase; searching said database for an existing entry that includessaid incident data; and transmitting the contents of said existing entryto said requestor in response to locating said existing entry.
 2. Themethod of claim 1, wherein said field solution data further includes arequester component.
 3. The method of claim 1, wherein said fieldsolution data further includes a requester measurement.
 4. The method ofclaim 1 wherein said field solution data further includes a requestermeasurement.
 5. The method of claim 1, further comprising evaluatingsaid field solution data for inclusion in said database.
 6. The methodof claim 5, wherein said evaluating includes a plurality of team membersviewing said field solution data and collaborating electronically. 7.The method of claim 5, further comprising: augmenting said database inresponse to said receiving field solution data and to said evaluating,wherein said augmenting includes: searching said database for anexisting entry that includes said field solution data; and updating anoccurrence field corresponding to said existing entry in response tolocating said existing entry in said database; or inserting a new entryinto said database in response to an indication that said field solutiondata was not located in said database, wherein said new entry includessaid field solution data.
 8. The method of claim 7, wherein saidoccurrence field includes a counter and said updating an occurrencefield includes incrementing said counter.
 9. The method of claim 1,wherein said database is imported from an external system containingfailure mode and effects analysis data.
 10. The method of claim 1,further including creating said database during product design.
 11. Themethod of claim 10, wherein said creating includes: performing failuremode and effects analysis; and populating said database in response tosaid performing.
 12. The method of claim 11, wherein said performingfailure mode and effects analysis includes utilizing a collaborationtool to reach consensus on said populating.
 13. The method of claim 1,wherein said requestor is a customer.
 14. The method of claim 1, whereinsaid requestor is a remote diagnostics engineer.
 15. The method of claim1, wherein said incident data further includes a requestor component.16. The method of claim 1, wherein said incident data further includes arequestor primary effect.
 17. The method of claim 1, wherein saidincident data further includes a requestor product level effect.
 18. Themethod of claim 1, wherein said database includes a product field, afault mode field, a corrective action field and an occurrence field. 19.The method of claim 18, wherein said database further includes acomponent field.
 20. The method of claim 18, wherein said databasefurther includes a primary effect field.
 21. The method of claim 18,wherein said database further includes a product level effect field. 22.The method of claim 18, wherein said database further includes ameasurement field.
 23. The method of claim 1, wherein said product isindustrial power distribution equipment.
 24. The method of claim 1,wherein said product is a turbine engine system.
 25. The method of claim1, wherein said product is an appliance.
 26. A system for performingfailure mode and effects analysis throughout the product life cycle, thesystem comprising: a network; a user system in communication with saidnetwork; a storage device including a shared failure mode and effectsanalysis database; and a host system in communication with said networkand said storage device, said host system including electroniccollaboration software to implement a method comprising: receivingincident data from a requestor on said user system, said incident dataincluding a requester product and a requester fault mode; accessing saiddatabase; searching said database for an existing entry that includessaid incident data; and transmitting the contents of said existing entryto said requestor on said user system in response to locating saidexisting entry.
 27. The system of claim 26, wherein said electroniccollaboration software includes instructions to implement a methodfurther comprising: receiving field solution data from said requester,said field solution data including said requestor product, saidrequestor fault mode and a requestor corrective action.
 28. The systemof claim 27, wherein said electronic collaboration software includesinstructions to implement a method further comprising: evaluating saidfield solution data for inclusion in said database.
 29. The system ofclaim 28, wherein said electronic collaboration software includesinstructions to implement a method further comprising: augmenting saiddatabase in response to said receiving field solution data and to saidevaluating, wherein said augmenting includes: searching said databasefor an existing entry that includes said field solution data; andupdating an occurrence field corresponding to said existing entry inresponse to locating said existing entry in said database; or insertinga new entry into said database in response to an indication that saidfield solution data was not located in said database, wherein said newentry includes said field solution data.
 30. The system of claim 26,wherein said electronic collaboration software includes instructions toimplement a method further comprising: performing failure mode andeffects analysis; and populating said database in response to saidperforming.
 31. The system of claim 26, wherein said network is theInternet.
 32. The system of claim 26, wherein said network is anintranet.
 33. The system of claim 26, wherein said storage device andsaid host system are located in different geographic locations andcommunicate via said network.
 34. The system of claim 26, wherein saiduser system and said host system are located in different geographiclocations.
 35. A computer program product for performing failure modeand effects analysis throughout the product life cycle, the computerproduct comprising: a storage medium readable by a processing circuitand storing instructions for execution by the processing circuit forperforming a method comprising: receiving field solution data from saidrequestor, said field solution data including said requestor product,said requestor fault mode, a requester corrective action and a requestorprimary effect; receiving incident data from a requester, said incidentdata including a requestor product and a requestor fault mode; accessinga shared failure mode and effects analysis database; searching saiddatabase for an existing entry that includes said incident data; andtransmitting the contents of said existing entry to said requestor inresponse to locating said existing entry.
 36. A method for performingfailure mode and effects analysis throughout the product life cycle, themethod comprising: receiving incident data from a requestor, saidincident data including a requestor product and a requestor fault mode;accessing a shared failure mode and effects analysis database; searchingsaid database for an existing entry that includes said incident data;and transmitting the contents of said existing entry to said requesterin response to locating said existing entry; wherein said product isindustrial power distribution equipment.
 37. A method for performingfailure mode and effects analysis throughout the product life cycle, themethod comprising: receiving incident data from a requester, saidincident data including a requester product and a requestor fault mode;accessing a shared failure mode and effects analysis database; searchingsaid database for an existing entry that includes said incident data;and transmitting the contents of said existing entry to said requestorin response to locating said existing entry; wherein said product is aturbine engine system.